One of the two techniques for communicating between parallel processes (the other being shared memory). A common use of message passing is for communication in a parallel computer. A process running on one processor may send a message to a process running on the same processor or another. The actual transmission of the message is usually handled by the run-time support of the language in which the processes are written, or by the operating system. Message passing scales better than shared memory, which is generally used in computers with relatively few processors. This is because the total communications bandwidth usually increases with the number of processors. A message passing system provides primitives for sending and receiving messages. These primitives may by either synchronous or asynchronous or both. A synchronous send will not complete (will not allow the sender to proceed) until the receiving process has received the message. This allows the sender to know whether the message was received successfully or not (like when you speak to someone on the telephone). An asynchronous send simply queues the message for transmission without waiting for it to be received (like posting a letter). A synchronous receive primitive will wait until there is a message to read whereas an asynchronous receive will return immediately, either with a message or to say that no message has arrived. Messages may be sent to a named process or to a named mailbox which may be readable by one or many processes. Transmission involves determining the location of the recipient and then choosing a route to reach that location. The message may be transmitted in one go or may be split into packets which are transmitted independently (e.g. using wormhole routing) and reassembled at the receiver. The message passing system must ensure that sufficient memory is available to buffer the message at its destination and at intermediate nodes. Messages may be typed or untyped at the programming language level. They may have a priority, allowing the receiver to read the highest priority messages first. Some message passing computers are the {MIT J-Machine (http://ai.mit.edu/projects/cva/cva_j_machine.html)}, the {Illinois Concert Project (http://www-csag.cs.uiuc.edu/projects/concert.html)} and transputer-based systems. Object-oriented programming uses message passing between objects as a metaphor for procedure call. (1994-11-11)

Expanded Memory Specification

<storage> (EMS) An IBM PC memory paging scheme enabling access to memory other than conventional memory in {real mode}. Expanded memory is provided through a page frame of at least 64 kilobytes in the reserved memory address region. Access to this memory is provided by an {expanded memory manager} (EMM) software. The EMM functions are accessible through interrupt 67H. In 8086 or 8088 based systems this is the only way to use memory beyond conventional memory. In systems based on 80286 or later, XMS and HMA provide alternative methods. EMS was developed jointly by Lotus, Intel, and Microsoft prior to 1988. Accordingly, this specification is sometimes referred to as LIM EMS. A complete discussion of EMS and programming examples can be found in ["PC System Programming for developers", 1989, ISBN 1-55755-035-2 (Book only) and ISBN 1-55755-036-0 (Book and diskette)]. EEMS, a competing expanded memory management standard, was developed by AST Research, Quadram and Ashton-Tate. See also upper memory block. (1996-01-10)